How to write PPC modules (Currently CodeWarrior C only).
Prelimanary draft 6/5/95 by Andrew Armstrong
There are two parts to your PPC native module. The first part is a 68k code resource that 'thunks' the call from the engine to the PPC native shared library. The second is the PPC shared libary that does the cool stuff.
StubMod.π has two input files - StubMod.c & StubMod.π.rsrc. StubMod.c loads in the PPC shared library, establishes a link, and passes on all of the AfterDark messages to your code. StubMod.π.rsrc has the error string that's displayed when your code is run on a 68k machine. The output of the project is 'StubModWarrior', a compiled resource file that you should include in your
JustOvals.π is an example of a simple PPC native module. The project type is a 'Shared Library' with a creator/type of "ADrk"/"ADgm". GraphicsModules.c is a good generic shell that you can use as a starting point for all of your modules. JustOvals.c is where the real work gets done. Besides these two 'c' files, 'StubModWarrior' is included and handles the transition from 68k to PPC.
6/29/95 (aea)
The "GraphicsModule_Types.h" file has been bracketed with the proper alignment pragmas.
If you have questions, please contact our tech support department.
